PhoenixFD 3.0 doesn`t handle user defined properties correct

[hardrock_ram]

PhoenixFD starts putting it`s own user defined properties on the same line as the previous entries.
As you can see in the screenshot, "theUDIM=1001" was written by me some time ago. On the same line, PHXFD continues with its own keyword. I don`t know if this causes problems for phoenix, but it certainly does for me.
PS: I can fix it quickly with maxScript, so it`s not a huge issue for me

[Svetlin.Nikolov]

Hey,

Thanks for catching this! I think it's a max thing though, since Phoenix gets and sets these through max and the newlines don't reach the Phoenix code so we can parse them and allow proper editing. I guess the workaround would be to always end your properties with a newline.

Cheers!

[hardrock_ram]

Can`t Phoenix run a maxScript code or something to make sure it gets correct? Like some sort of cleanup ... I know its ugly, but its better than nothing.

[Svetlin.Nikolov]

If we had access to the entire text we could do anything, but right now we just ask Max: "Max, do you have *that* user prop?" - "Yes/No" - "Okay, give us the value of that prop" - "Here you go" - and that's pretty much it.

I'm gonna check if there is some other way to do it

[Svetlin.Nikolov]

Yup, seems like 3ds Max just does not sanitize the properties string before editing it through the SDK - you will have the same issue with the V-Ray per-node props as well, unless you place a newline at the end. Will file this issue into our bugtracker as there is a way to work around it, but it's rather hacky.

[Svetlin.Nikolov]

Alright, got it! Will be in tomorrow's nightly

[vlado]

We had the same issue with the V-Ray proxies and some user-defined properties that they write...

Best regards,
Vlado